Presenting a modal dialog box using an invisible panel underneath

ABSTRACT

Techniques for presenting a modal dialog box in a graphical user interface are described herein. According to one embodiment, a semi-transparent panel is displayed superimposed on a graphical user interface (GUI) page in response to a first user interaction with the GUI page. The GUI page provides a user interface for managing a virtualization system. A dialog box is then displayed on top of the semi-transparent panel, where the dialog box is to receive an input from the user. An alert is generated in response to a second user interaction with an area of the semi-transparent panel other than the dialog box, where the alert indicates that the second user interaction is invalid.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims the benefit of U.S.patent application Ser. No. 12/491,052, filed Jun. 24, 2009, which isincorporated by reference herein.

COPYRIGHT NOTICES

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

Embodiments of the present invention relates generally to graphical userinterfaces. More particularly, embodiments relate to techniques forpresenting a modal dialog box using an invisible panel underneath.

BACKGROUND

Most modern computer software employs a graphical user interface (“GUI”)to convey information to and receive commands from users. A graphicaluser interface relies on a variety of GUI objects or controls, includingicons, toolbars, drop-down menus, text, dialog boxes, buttons, and thelike. A dialog box can be in either a modal style or a non-modal style.

Modal dialog boxes require all user interactions to be focused withinthe dialog box, and usually include an OK button and/or a Cancel button.Modal dialog boxes are used when an application, utility, tool, commandor other means requires information before the application can continue,such as a file name, or when a complete set of information is requiredbefore proceeding, or when a message such as an alert or warning isgiven. Modal dialog boxes must be dismissed or closed before the usercan proceed with further actions. Conversely, non-modal dialog boxespermit a user to interact with other dialog boxes or other parts of anapplication, such as with drawing tools. The controls in non-modaldialog boxes can be adjusted at any time, and non-modal dialog boxes donot have to be closed or dismissed before continuing work.

Typically, when a modal dialog box is required, a user interfacefunction such as that provided as a part of software development kit(SDK) (e.g., a Java applet) is invoked which provides a modal dialogbox. However, under certain circumstances, e.g., in an HTML (hypertextmarkup language) page of a Web application, such a function or SDK maynot be available.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and notlimitation in the figures of the accompanying drawings in which likereferences indicate similar elements.

FIG. 1 is a block diagram illustrating an example of a networkconfiguration according to one embodiment of the invention.

FIGS. 2A and 2B are screenshots illustrating an example of GUI having amodal dialog box according to certain embodiments of the invention.

FIG. 3 is a block diagram illustrating an example of a control serveraccording to one embodiment.

FIG. 4 is a flow diagram illustrating a method for presenting a modaldialog box according to another embodiment.

FIG. 5 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system which may be used with an embodimentof the invention.

DETAILED DESCRIPTION

Techniques for presenting a modal dialog box in a graphical userinterface are described herein. In the following description, numerousdetails are set forth to provide a more thorough explanation of theembodiments of the present invention. It will be apparent, however, toone skilled in the art, that embodiments of the present invention may bepracticed without these specific details. In other instances, well-knownstructures and devices are shown in block diagram form, rather than indetail, in order to avoid obscuring embodiments of the presentinvention.

Reference in the specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the invention. The appearances of the phrase “in one embodiment” invarious places in the specification do not necessarily all refer to thesame embodiment.

As described above, typically when a modal dialog box is required, auser interface function such as that provided as a part of SDK isinvoked which provides a modal dialog box. However, under certaincircumstances, e.g., in an HTML page of a Web application or a Windowspresentation foundation (WPF) application, there is no solution orsupport for a modal dialog. In some situations, the lack of modal dialogfeatures may cause an undesirable experience to a user.

According to one embodiment, a custom dialog is constructed or drawnfrom a regular panel or a built-in dialog where the custom dialogbehaves like a modal dialog. In a particular embodiment, when a requestfor displaying a modal dialog box is received, for example, in responseto a user interaction with a GUI page such as a Web page presented by asoftware application or a WPF application, a semi-transparent panel isconstructed and displayed superimposed on the GUI page. Thereafter, adialog box is displayed on the top of the semi-transparent panel. Thedialog box may be constructed or drawn from a regular panel or abuilt-in dialog which would normally behaves like a modaless dialog. Thesemi-transparent panel, which when placed superimposed on the GUI page,darkens or modifies (e.g., reduce) a display resolution of the GUI pagewhich gives an impression to a user that areas of the GUI page outsideof the dialog box are inaccessible.

In addition, when the user interacts with (e.g., click) those areas ofthe GUI page outside of the dialog box, a user interface module (e.g.,event handler) of the software application would not react to such userinteractions. Alternatively, the software application may generate analert indicating that such an action is invalid. For example, such analert may be presented in a visual form such as changing a shape of amouse (e.g., hour glass shape) or alternatively in an audible form(e.g., a beep). As a result, the semi-transparent panel in combinationwith the dialog box simulates a modal dialog box in an environment inwhich a corresponding GUI function is unavailable.

According to one embodiment, the above described modal dialog boximplementation may be utilized in a virtualization system such as agraphics remoting or virtual desktop application such as SolidICE™available from Red Hat. Alternatively it can be implemented as part of aGUI for a management function of a virtualization system such as avirtual desktop control (VDC) server.

FIG. 1 is a block diagram illustrating an example of a networkconfiguration according to one embodiment of the invention. Referring toFIG. 1, network configuration 100 includes, but is not limited to, oneor more clients 101 communicatively coupled to a remote server or acluster of servers 104 over a network 103. Network 103 may be a localarea network (LAN) or a wide area network (WAN) and may be a combinationof one or more networks. Client 101 can be any computer system incommunication with server 104 for remote execution of applications atserver 104.

For example, system 100 may be implemented as part of a graphicsremoting system. Generally, a client such as client 101 can be acomputer system in communication with server 104 for remote execution ofapplications at server 104. Thus, input data (e.g., mouse and keyboardinput) representing application commands is received at the client andtransferred over network 103 to server 104. In response to client sidedata, an application (e.g., desktop application 108) can generate outputdisplay commands (e.g., graphics commands, simply referred to herein asgraphics data), which may include one or more paint and/or drawoperations, for example, in the form of executable instructions. Theoutput display commands can then be transmitted (e.g., as graphicsupdate commands) with an optional compression by remote display system109 back to the remote client and a remote rendering agent 106 of theremote client can collect the graphics commands and generatecorresponding drawing commands for rendering at a display device of theclient. Note that a desktop application is utilized herein as anexample; however, any other application may also be applied. [0020] Inone embodiment, server 104 is configured to host one or more virtualmachines 107, each having one or more desktop applications 108 (e.g.,desktop operating system). Desktop application 108 may be executed andhosted by an operating system within virtual machine 107. Such anoperating system in virtual machine 107 is also referred to as a guestoperating system. Multiple guest operating systems and the associatedvirtual machines may be controlled by another operating system (alsoreferred to as a host OS). Typically, a host OS represents a virtualmachine monitor (VMM) (also referred to as a hypervisor) for managingthe hosted virtual machines. A guest OS may be of the same or differenttype with respect to the host OS. For example, a guest OS may be aWindows™ operating system from Microsoft and a host OS may be a Linuxoperating system available from Red Hat.

Virtual machine 107 can be any type of virtual machines, such as, forexample, hardware emulation, full virtualization, para-virtualization,and operating system-level virtualization virtual machines. Differentvirtual machines hosted by server 104 may have the same or differentprivilege levels for accessing different resources.

System 100 may be implemented as part of a server or a cluster ofservers within a data center of an enterprise entity. It allowsenterprises the benefit of centralized desktops without the need tochange their applications or infrastructure. Enterprises benefit from animprovement in the manageability, security and policy enforcement fortheir desktop environment, and consequently, realize a significantreduction in the desktop TCO (total cost of ownership).

Host server 104 and client 101 may be managed by a control server 102(also referred to as a management server or system). For example, in agraphics remoting application, host server 104 may be implemented as aVDS server while control server 102 may be implemented as a VDC (virtualdesktop control) server.

In one embodiment, control server 102 includes a virtualization manager110 and a graphical user interface 112 to allow a user such as anadministrator to access the virtualization manager 110. Virtualizationmanager 110 is configured to control virtual machines (e.g., virtualdesktop solutions), including provisioning, connection protocol, usersession logon/logoff, virtual desktop pools, virtual desktop images, andhigh availability/clustering system. A user (e.g., an administrator) mayaccess the virtualization manager 110 via GUI 112 to perform at leastsome of the above-mentioned functions. A GUI page may be constructed asan HTML page or a WPF page which can be rendered and displayed via abrowser, such as, for example, GUI pages as shown in FIGS. 2A and 2B.

According to one embodiment, in response to a user interaction with aGUI page such as the one shown in FIG. 2A, it is determined whether theuser interaction should cause a modal dialog box to be displayed. Inthis example, a user may activate a button or control (e.g., text-box,select-box, or other input controls) on the GUI page, such as a “new”button 201 on GUI page 200 as shown in FIG. 2A for creating a new hostfor hosting a VM, as it requires a user to enter certain parameters forthe new host before moving forward. If it is determined that a modaldialog box is to be displayed, according to one embodiment, asemi-transparent panel is constructed and displayed on the top of GUIpage 200 as shown in FIG. 2B. Referring to FIG. 2B, the semi-transparentpanel 202 is displayed on the top of GUI page 200, giving an impressionthat the buttons or controls of GUI page 200 are not accessible.Thereafter, a dialog box 203 is displayed on the top of thesemi-transparent panel 202. The dialog box 203 may be constructed ordrawn from a regular panel or a built-in dialog that would normallybehaves like a modaless dialog.

In this example, there is no reaction to a user interaction with an areaof the semi-transparent panel 202 that is outside of the dialog box 203.Since the semi-transparent panel 202 is displayed on the top of GUI page200, when a user clicks on the semi-transparent panel 202, a user eventhandler associated with the semi-transparent panel 202 will receive acorresponding event (e.g., a mouse click event). The event handler ofthe semi-transparent panel 202 may ignore the event by doing nothing.Alternatively, the event handler may perform certain actions such asgenerating an alert (e.g., visual or audio alert) indicating that such auser interaction is invalid. As a result, an event handler associatedwith the underneath GUI page 200 will not receive any user events. Thecorresponding software application can only continue when the useractivates a control within the dialog box 203, for example, by clickingthe OK or Cancel button.

Therefore, a combination of the semi-transparent panel 202 and dialogbox 203 represents a modal dialog box, without a need of certain SDK ordevelopment framework to create the same. Note that the semi-transparentpanel 202 does not have to be semi-transparent. It can be fullytransparent. By making panel 202 semi-transparent, it gives a user animpression that the underneath functionalities of GUI page 200 areinaccessible. Other configurations may exist. Also note that the abovemodal dialog box techniques may also be applied in other GUIapplication, such as, for example, content of a graphics remotingapplication displayed at a client (e.g., client 101).

FIG. 3 is a block diagram illustrating an example of a control serveraccording to one embodiment. For example, system 300 may be implementedas part of control server 102 of FIG. 1. In one embodiment, system 300includes, but is not limited to, a graphical user interface 301 (e.g.,GUI 112 of FIG. 1) and a virtualization manager 302 (virtualizationmanager 110 of FIG. 1). In one embodiment, the administration unit 305together with GUI 301 may provide an administration portal (e.g., a Webportal) to allow an administrator to log in and perform certainadministrative functions, such as, for example, managing virtualmachines (e.g., virtual desktop solutions), including provisioning,connection protocol, user session logon/logoff, virtual desktop pools,virtual desktop images, and high availability/clustering system.

According to one embodiment, an administrator can communicate withadministration unit 305 via GUI 301. For example, an administrator cancreate or provision a new host via GUI 301, similar to GUI pages shownin FIGS. 2A and 2B. GUI 301 includes a user interface event handler 303and a modal dialog box constructor 304. The event handler 303 isconfigured to receive a user interaction from a GUI page as an event(e.g., a click event) and to interpret and/or pass a command associatedwith the event to administration unit 305 for further processing.

According to one embodiment, in response to a user interaction with aGUI page such as the one shown in FIG. 2A, it is determined via eventhandler 303 whether the user interaction should cause a modal dialog boxto be displayed. If it is determined that a modal dialog box is to bedisplayed, according to one embodiment, modal dialog box constructor 304is configured to construct a semi-transparent panel and thesemi-transparent panel is displayed on the top of GUI page 200 as shownin FIG. 2B, giving an impression that certain buttons or controls (e.g.,button 201) of GUI page 200 are not accessible. Thereafter, a dialog boxis displayed on the top of the semi-transparent panel. The dialog boxmay be constructed or drawn from a regular panel or a built-in dialogthat would normally behaves like a modaless dialog

In this example, there is no reaction to a user interaction with an areaof the semi-transparent panel that is outside of the superimposed dialogbox. Since the semi-transparent panel is displayed on top of the GUIpage, when a user clicks on the semi-transparent panel, event handler303 will receive a corresponding event (e.g., a mouse click event). Theevent handler 303 may simply ignore the event by doing nothing.Alternatively, the event handler 303 may perform certain actions such asgenerating an alert (e.g., visual or audio alert) indicating that such auser interaction is invalid. As a result, an event handler associatedwith the underneath GUI page will not receive any user events. Thecorresponding software application can only continue when the useractivates an area within the dialog box, for example, by clicking the OKor Cancel button. Note that some or all of the components as shown inFIG. 3 may be implemented in software, hardware, or a combination ofboth.

Note that virtualization manager 302 can also perform a variety of othervirtualization management functions. For example, virtualization manager302 may associate a VM with a client when the client registers with thesystem 300. As a result, a VM can be automatically launched by system300 for a client, either sequentially after the client has started up orin parallel in a remote host while the client is starting up.

FIG. 4 is a flow diagram illustrating a method for presenting a modaldialog box according to one embodiment. Note that method 400 may beperformed by processing logic which may include software, hardware, or acombination of both. For example, method 400 may be performed by system300 of FIG. 3. Referring to FIG. 4, at block 401, a graphical userinterface page (e.g., FIG. 2A) is presented to a user such as anadministrator, for example, for managing a virtualization system. Inresponse to a user interaction with the GUI page, at block 402,processing logic determines whether a modal dialog box is to bepresented. If it is determined that a modal dialog box is to bepresented, at block 403, a semi-transparent panel is constructed anddisplayed on the top of the GUI page, giving the user an impression thatcertain features of the GUI page are inaccessible. At block 404, adialog box is displayed on the top of the semi-transparent panel (e.g.,FIG. 2B). The dialog box may be constructed or drawn from a regularpanel or a built-in dialog that would normally behaves like a modalessdialog. In response to a user interaction with the semi-transparentpanel other than the dialog box, at block 405, an alert is generatedindicating that the user interaction is invalid. The alert may be in avisual or audible form.

FIG. 5 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system 800 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine may be connected (e.g., networked) to othermachines in a LAN, an intranet, an extranet, and/or the Internet. Themachine may operate in the capacity of a server or a client machine inclient-server network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine may be apersonal computer (PC), a tablet PC, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, aserver, a network router, a switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The exemplary computer system 800 includes a processing device 802, amain memory 804 (e.g., read-only memory (ROM), flash memory, dynamicrandom access memory (DRAM) such as synchronous DRAM (SDRAM) or RambusDRAM (RDRAM), etc.), a static memory 806 (e.g., flash memory, staticrandom access memory (SRAM), etc.), and a data storage device 816, whichcommunicate with each other via a bus 808.

Processing device 802 represents one or more general-purpose processingdevices such as a microprocessor, a central processing unit, or thelike. More particularly, the processing device may be complexinstruction set computing (CISC) microprocessor, reduced instruction setcomputing (RISC) microprocessor, very long instruction word (VLIW)microprocessor, or processor implementing other instruction sets, orprocessors implementing a combination of instruction sets. Processingdevice 802 may also be one or more special-purpose processing devicessuch as an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA), a digital signal processor (DSP),network processor, or the like. The processing device 802 is configuredto execute the instructions 826 for performing the operations and stepsdiscussed herein.

The computer system 800 may further include a network interface device822. The computer system 800 also may include a video display unit 810(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), analphanumeric input device 812 (e.g., a keyboard), a cursor controldevice 814 (e.g., a mouse), and a signal generation device 820 (e.g., aspeaker).

The data storage device 816 may include a computer-accessible storagemedium 824 (also known as a machine-readable storage medium or acomputer-readable medium) on which is stored one or more sets ofinstructions or software 826 embodying any one or more of themethodologies or functions described herein. The software 826 may alsoreside, completely or at least partially, within the main memory 804and/or within the processing device 802 during execution thereof by thecomputer system 800, the main memory 804 and the processing device 802also constituting machine-accessible storage media. The software 826 mayfurther be transmitted or received over a network via the networkinterface device 822.

Thus, techniques for presenting a modal dialog box in a graphical userinterface have been described herein. Some portions of the precedingdetailed descriptions have been presented in terms of processes andsymbolic representations of operations on data bits within a computermemory. These process descriptions and representations are the ways usedby those skilled in the data processing arts to most effectively conveythe substance of their work to others skilled in the art. A process ishere, and generally, conceived to be a self-consistent sequence ofoperations leading to a desired result. The operations are thoserequiring physical manipulations of physical quantities. Usually, thoughnot necessarily, these quantities take the form of electrical ormagnetic signals capable of being stored, transferred, combined,compared, and otherwise manipulated. It has proven convenient at times,principally for reasons of common usage, to refer to these signals asbits, values, elements, symbols, characters, terms, numbers, or thelike.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the above discussion, itis appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

Embodiments of the present invention also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, or it may comprise ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program may bestored in a computer readable medium. A machine-readable medium includesany mechanism for storing or transmitting information in a form readableby a machine (e.g., a computer). For example, a machine-readable (e.g.,computer-readable) medium includes a machine (e.g., a computer) readablestorage medium (e.g., read only memory (“ROM”), random access memory(“RAM”), magnetic disk storage media, optical storage media, flashmemory devices), etc.

The processes and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general-purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method operations. The requiredstructure for a variety of these systems will appear from thedescription above. In addition, embodiments of the present invention arenot described with reference to any particular programming language. Itwill be appreciated that a variety of programming languages may be usedto implement the teachings of embodiments of the invention as describedherein.

In the foregoing specification, embodiments of the invention have beendescribed with reference to specific exemplary embodiments thereof. Itwill be evident that various modifications may be made thereto withoutdeparting from the broader spirit and scope of embodiments of theinvention as set forth in the following claims. The specification anddrawings are, accordingly, to be regarded in an illustrative senserather than a restrictive sense.

What is claimed is:
 1. A method comprising: displaying, by a processingdevice, a panel superimposed on a graphical user interface (GUI)virtualization system management page; displaying on top of the panel adialog box comprising an input user interface element; receiving, by anevent handler of the panel, an event associated with a user interactionwith the panel outside of the dialog box; generating, by the processingdevice, an alert in response to the user interaction indicating that theuser interaction is invalid, wherein the alert is in a visual form; andpreventing an event handler of the GUI virtualization system managementpage from receiving the event.
 2. The method of claim 1, wherein thepanel indicates that at least one control of the GUI virtualizationsystem management page is inaccessible.
 3. The method of claim 2,wherein a semi-transparent panel reduces an overall display resolutionof the GUI virtualization system management page.
 4. The method of claim1, wherein the alert is also generated in an audible form.
 5. The methodof claim 1, wherein a user interacts with a semi-transparent paneloutside of the dialog box, an event associated with the user interactionis received by an event handler of the semi-transparent panel withoutproviding the event to an event handler of the GUI virtualization systemmanagement page underneath.
 6. The method of claim 1, wherein the GUIvirtualization system management page is presented as part of a Webportal of a virtualization management system and a Windows presentationfoundation (WPF) application, wherein the virtualization managementsystem is to manage a virtual machine for a client.
 7. The method ofclaim 6, further comprising receiving a user interaction activating acontrol of the GUI virtualization system management page for creating ahost which requires a certain parameter to proceed for hosting a virtualmachine.
 8. A non-transitory computer readable storage medium includinginstructions that, when executed by a processing device, cause theprocessing device to execute operations comprising: displaying, by theprocessing device, a panel superimposed on a graphical user interface(GUI) virtualization system management page; displaying on top of thepanel a dialog box comprising an input user interface element;receiving, by an event handler of the panel, an event associated with auser interaction with the panel outside of the dialog box; generating,by the processing device, an alert in response to the user interactionindicating that the user interaction is invalid, wherein the alert is ina visual form; and preventing an event handler of the GUI virtualizationsystem management page from receiving the event.
 9. The non-transitorycomputer readable storage medium of claim 8, wherein the panel indicatesthat at least one control of the GUI virtualization system managementpage is inaccessible.
 10. The non-transitory computer readable storagemedium of claim 9, wherein a semi-transparent panel reduces an overalldisplay resolution of the GUI virtualization system management page. 11.The non-transitory computer readable storage medium of claim 8, whereinthe alert is also generated in an audible form.
 12. The non-transitorycomputer readable storage medium of claim 8, wherein a the userinteracts with a semi-transparent panel outside of the dialog box, anevent associated with the user interaction is received by an eventhandler of the semi-transparent panel without providing the event to anevent handler of the GUI virtualization system management pageunderneath.
 13. The non-transitory computer readable storage medium ofclaim 8, wherein the GUI virtualization system management page ispresented as part of a Web portal of a virtualization management systemand a Windows presentation foundation (WPF) application, wherein thevirtualization management system is to manage a virtual machine for aclient.
 14. The non-transitory computer readable storage medium of claim13, further comprising receiving a user interaction activating a controlof the GUI virtualization system management page for creating a hostwhich requires a certain parameter to proceed for hosting a virtualmachine.
 15. A system, comprising: a display device; a processing devicecoupled to the display device; and a memory coupled to the processingdevice to store computer instructions, which when executed from thememory, cause the processing device to: display a panel superimposed ona graphical user interface (GUI) virtualization system management page,display on top of the panel a dialog box comprising an input userinterface element, receive, by an event handler of the panel, an eventassociated with a user interaction with the panel outside of the dialogbox; generate an alert in response to the user interaction indicatingthat the user interaction is invalid, wherein the alert is in a visualform; and prevent an event handler of the GUI virtualization systemmanagement page from receiving the event.
 16. The system of claim 15,wherein the panel indicates that at least one control of the GUIvirtualization system management page is inaccessible.
 17. The system ofclaim 16, wherein a semi-transparent panel reduces an overall displayresolution of the GUI virtualization system management page.
 18. Thesystem of claim 15, wherein the alert is also generated in an audibleform.
 19. The system of claim 15, wherein a the user interacts with asemi-transparent panel outside of the dialog box, an event associatedwith the user interaction is received by an event handler of thesemi-transparent panel without providing the event to an event handlerof the GUI virtualization system management page underneath.
 20. Thesystem of claim 15, wherein the GUI virtualization system managementpage is presented as part of a Web portal of a virtualization managementsystem and a Windows presentation foundation (WPF) application, whereinthe virtualization management system is to manage a virtual machine fora client.